You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When creating reusable importable components it would be useful to have a ###ZARF_COMPONENT_NAME### template / variable that can be used to scope that component properly.
Describe the solution you'd like
Given I have a zarf.yaml with ###ZARF_COMPONENT_NAME### in a string value
When I run zarf package create on that package
Then Zarf will template that value with that component's name
Describe alternatives you've considered
We could do this on deploy time or in another way, but most scoping would be around variables or actions and this would be easier / more declarative to do create-time.
Additional context
This would make things like a reusable S3 bucket component easier to make.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When creating reusable importable components it would be useful to have a
###ZARF_COMPONENT_NAME###
template / variable that can be used to scope that component properly.Describe the solution you'd like
zarf.yaml
with###ZARF_COMPONENT_NAME###
in a string valuezarf package create
on that packageDescribe alternatives you've considered
We could do this on deploy time or in another way, but most scoping would be around variables or actions and this would be easier / more declarative to do create-time.
Additional context
This would make things like a reusable S3 bucket component easier to make.
The text was updated successfully, but these errors were encountered: