-
Notifications
You must be signed in to change notification settings - Fork 27
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
Move DFX Beta implementation to GA process #31
Conversation
Cdpy: * Rework cdpy/df to use the 'service' nomenclature instead of 'environment' for DataFlow * Allow separate submission of a name, env_crn, or df_crn for filtering the list of enabled DataFlow services * Allow submission of an env_crn or df_crn for the description of a Dataflow Service, as you cannot know the df_crn during creation until it is actually created * Standardise on use of df_crn for the service crn in DataFlow to provide differentiation from the env crn and other crns in CDP * Add new service enablement parameters to the dfx enable_service call * Add new terminate option to the DFX disable_service call * Change delete_environment to reset_service to reflect new usage * Squelch 403 response on describing a recently deleted Dataflow Service while it is being cleaned up cloudera.cloud: * renamed df.py to df_service.py to reflect that other DataFlow modules for Deployments will be needed in future * Include changes to submission parameters and method names for 'cdp df' calls in cdpy * Modify enable and disable service logic to match new methods and parameters * df_info now supports name, df_crn, or env_crn for filtering results * env_info once again checks for DataFlow during detailed Environment information collection * Added input validation for DataFlow service creation cloudera.exe: * Added defaults handling for new DataFlow submission parameters * renamed various methods and parameters to reflect updated DataFlow service naming and options Signed-off-by: Daniel Chaffelson <chaffelson@gmail.com>
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.
Minor changes. Really hate to commit the scope creep of env_info
/one-ring-to-rule-them-all.
@@ -436,7 +436,7 @@ def process(self): | |||
for this_env in self.environments: | |||
df = None | |||
# Removing until DF is GA so we are not dependent on Beta functionality | |||
# df = self.cdpy.df.describe_environment(this_env['crn']) | |||
df = self.cdpy.df.list_services(env_crn=this_env['crn']) |
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.
This is scope creep! #21
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.
Currently safe delete of an environment relies on this functionality, agree that it should be cleaned up to not need it but I don't want to cross the streams.
Add terminate option to docs for df_service.py Add additional options to examples/cdf for df service Signed-off-by: Daniel Chaffelson <chaffelson@gmail.com>
Dependencies:
cloudera-labs/cdpy#30
cloudera.cloud:
Signed-off-by: Daniel Chaffelson chaffelson@gmail.com