Skip to content

Conversation

ptiurin
Copy link
Contributor

@ptiurin ptiurin commented Feb 9, 2022

Allowing special parameters like db_version, proxy_version which are part of the API, but should be obfuscated from the external user. As discussed we're fine if users find out about them via reading the code, but reading the docs should not give hints about their existence.
This will mainly be used for automated testing by internal teams.

specification=EngineRevisionSpecification(
db_compute_instances_type_key=instance_type_key,
db_compute_instances_count=scale,
db_compute_instances_use_spot=False,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we wan't to have some defaults for db_compute_instances_use_spot, db_version, proxy_instances_count and proxy_version?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already have those defaults in EngineRevisionSpecification,

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

85.6% 85.6% Coverage
0.0% 0.0% Duplication

@ptiurin ptiurin merged commit ab49223 into main Feb 14, 2022
@ptiurin ptiurin deleted the enh-internal-params-engine branch February 14, 2022 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants