-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-generated actions for #3 #4
Auto-generated actions for #3 #4
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding #3 about the action names. Separating compute_profiles_compute_attributes_compute_profile_id_compute_updateresources
with a dot after the endpoint. What do you think? compute_profile.compute_attribute_...
enabled: true | ||
runner_type: "python-script" | ||
entry_point: lib/action.py | ||
name: compute_profiles_compute_attributes_compute_profile_id_compute_updateresources |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what i meant in #3 . Might be very hard to read
@nullkarma Updated to have the format: |
Merge from upstream into this fork
Wanted to separate out the auto-generated action noise from the base code that does the real "work".
Note: this depends on #3