Skip to content

Conversation

@Aryanag2
Copy link
Member

Improve Handling of Default SMM Parameters for Model Deployment (UI & Backend)

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Nov 25, 2025
@github-actions
Copy link

📌 Cov diff with main:

Coverage-0%

📌 Overall coverage:

Coverage-17.89%

@github-actions
Copy link

📌 Cov diff with main:

Coverage-0%

📌 Overall coverage:

Coverage-17.89%

@mrDzurb mrDzurb changed the title deployment params [AQUA] Improve Handling of Default SMM Parameters for Model Deployment Dec 2, 2025
config_parameters = item.parameters.get(

# If user DID NOT provide specific params (None or Empty), we look for defaults
if not user_params:
Copy link
Member

Choose a reason for hiding this comment

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

Will this cover the case where a user removes all default params in the UI? Which params will be applied then? The expectation is that SMM default params should not be used in that scenario. Basically only service params coming from the container level should be used in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants