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.
In large environments, running the full pipeline takes hours. This discourage customers to use the native LZA configuration files. It would be nice to be able to run simple changes (e.g. adding a new role, adding a new permissionSet, a new assignment etc.) without having the run the full pipeline (or having to stop its execution once the required stage is finished).
Describe the feature you'd like
Being able to re-run a single stage of the pipeline (e.g. security or organization) once a configuration change has been made.
Additional context
It's also more environmental friendly and uses less resources ;)
The text was updated successfully, but these errors were encountered:
Hello @thi-baut and thank you for raising this issue!
In our most recent release (v.1.3.0), we added some additional information to DEVELOPING.md that should help you target specific accelerator pipeline stages using our CLI scripts. Please let us know if this satisfies your requirements.
Is your feature request related to a problem? Please describe.
In large environments, running the full pipeline takes hours. This discourage customers to use the native LZA configuration files. It would be nice to be able to run simple changes (e.g. adding a new role, adding a new permissionSet, a new assignment etc.) without having the run the full pipeline (or having to stop its execution once the required stage is finished).
Describe the feature you'd like
Being able to re-run a single stage of the pipeline (e.g. security or organization) once a configuration change has been made.
Additional context
It's also more environmental friendly and uses less resources ;)
The text was updated successfully, but these errors were encountered: