Tags as building block inputs | Feature Requests

Tags as building block inputs

planned

Felix

I want to use tag values (like the environment the tenant is in) in my building block definitions.

Depending on the environment, my building block can be multi-region for prod (higher availability) or single-region for dev (cheaper) in the case of storage.

December 7, 2023

Jelle den Burger

marked this post as

planned

We see the value of this feature and plan to implement this in Q1 of 2025. Stay tuned!

Felix

Tags could be handed over just as a value (this would be preferable in my opinion).

A potentially easier to build alternative would be to have one source type that contains all tags + values (like for input type user permissions): https://docs.meshcloud.io/docs/administration.building-blocks.html#building-block-inputs

Felix

There are two workarounds for this:

repeat already known information
setting things static and duplicating building block definitions

One of the principals for good user experience is to never force users to repeat themselves, which we will get closer to with allowing to use tag values in your automations.

Julia Rengshausen

Felix This! Right now we are forcing users to repeat the number of their cost center. Not a great user experience.

Jelle den Burger

Thanks a lot for your idea Felix.
We are already planning to do this but unfortunately I cannot tell you yet when this happens.
What use cases do you have planned for using tag values in Building Blocks?

Karsten Pilz

Jelle den Burger We have a use-case where we like to get the tag values which we defined in projects into a building block which creates a template for AWS AFT. This approach makes AFT a lot more stable since you could mess up AFT pipelines with wrong templates. Via meshstack we ensure data quality for the templates and one part of this would be to use the tags.