Skip to content
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

add mlstudio integ tests #1535

Merged
merged 3 commits into from
Sep 13, 2024
Merged

add mlstudio integ tests #1535

merged 3 commits into from
Sep 13, 2024

Conversation

petrkalos
Copy link
Contributor

@petrkalos petrkalos commented Sep 11, 2024

Feature or Bugfix

Feature

Detail

Adding integration tests for ML Studio

PENDING TESTS PASSING IN DEV AWS ENV

Relates

related to #1220 and resolves #1534

Security

Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

  • Does this PR introduce or modify any input fields or queries - this includes
    fetching data from storage outside the application (e.g. a database, an S3 bucket)?
    • Is the input sanitized?
    • What precautions are you taking before deserializing the data you consume?
    • Is injection prevented by parametrizing queries?
    • Have you ensured no eval or similar functions are used?
  • Does this PR introduce any functionality or component that requires authorization?
    • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
    • Are you logging failed auth attempts?
  • Are you using or adding any cryptographic features?
    • Do you use a standard proven implementations?
    • Are the used keys controlled by the customer? Where are they stored?
  • Are you introducing any new policies/roles/users?
    • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

if errors := r.json().get('errors'):
raise GqlError(errors)
r.raise_for_status()
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Irrelevant change to first check for any errors and then raise for status. Sometimes the returned code when there are errors is not 2xx.

@petrkalos petrkalos marked this pull request as draft September 11, 2024 12:44
@petrkalos petrkalos marked this pull request as ready for review September 12, 2024 12:40

@pytest.fixture(scope='session')
def smstudio_user1(session_id, client1, persistent_env1):
env_uri = persistent_env1.environmentUri
Copy link
Contributor

Choose a reason for hiding this comment

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

Don't we have to ensure the create_environment API call has {'key': 'mlstudioEnabled', 'value': 'true'}, as part of parameters?

Otherwise we wouldn't be able to spin up mew sm studio users

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes you are right, I enabled it manually on my persistent environment and forgot to add it in code

Copy link
Contributor

@noah-paige noah-paige left a comment

Choose a reason for hiding this comment

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

Left a comment around creating env ensuring ML Studio is enabled.

Ideally we only enable on the 1 persistent env and not on the session envs so we do not need to add additional wait time for create SM Studio Domains for each env which would be lengthy

Otherwise code looks good - will try out the tests in meantime

Copy link
Contributor

@noah-paige noah-paige left a comment

Choose a reason for hiding this comment

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

looks good and tests passing on my aws deployment too - approved

@petrkalos petrkalos merged commit 3d4d648 into main Sep 13, 2024
9 checks passed
@petrkalos petrkalos deleted the feature/mlstudio_integtests branch September 13, 2024 14:38
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.

Integration tests executed on a real deployment as part of the CICD - MLStudio
2 participants