Add user to group (Non Production) #140
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…and will return base64 encoded string of file contents.
|
✅ Valid PR for ActionPack Thank you for your contribution. This PR complies with the CONTRIBUTING.md. |
deleting the unintended file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This FD Action will be useful in those use cases where group assignment and user access needs to be automated for non-production instances.
Consider a use case where for every new onboarding user need go to portal and make requests to get access to certain modules by requesting access to dedicated permission group this will end up days of effort to get approval review and get processed.
But what if you have a dedicated catalog item for non-prod acess request that will be invoked by flow that call action based on instance name access is requested for, amazing right!!! By looking up connection & credential alias for instance URL it can target the instance and update the access.
How it works?
See this execution for more info.
Happy to add more details f required further clarification.