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
Originally posted by jeff-mccoy September 24, 2021
Currently only zarf-init has the ability to deploy what is in the zarf package and optional additional groups of assets called features. Providing this capability to regular zarf packages as well wouldn't be difficult, but would allow greater flexibility with package creation. The only issue would be needing to resolve the use of local vs remote in the zarf config, #40 (comment).
Discussed in #63
Originally posted by jeff-mccoy September 24, 2021
Currently only
zarf-init
has the ability to deploy what is in the zarf package and optional additional groups of assets called features. Providing this capability to regular zarf packages as well wouldn't be difficult, but would allow greater flexibility with package creation. The only issue would be needing to resolve the use oflocal
vsremote
in the zarf config, #40 (comment).Example usage in zarf init yaml
How this would look for an example package, tiny-kafka
The text was updated successfully, but these errors were encountered: