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

Chore: Validate Content plugin settings #525

Merged

Conversation

iLLiCiTiT
Copy link
Member

@iLLiCiTiT iLLiCiTiT commented May 20, 2024

Changelog Description

Added profile based settings for Validate Content publish plugin.

Additional info

The settings will change behavior of the plugin based on host name. The plugin is disabled if host does not support load functionality, or there are no profiles. Removed settings of the plugin from other hosts.

We should do this for the move of hosts. The first encounter happened in #516 .

Testing notes:

  1. Create package of core and all changed host addons (AE, PS, Nuke, Maya, Houdini, Harmony).
  2. Launch DCC of one of the host integrations.
  3. Validate Content should be there and can be disabled (with default settings).
  4. Based on changed settings the plugin should change it's state -> remove all profiles, remove the host from list, add new hosts, change optional state etc.

@ynbot
Copy link
Contributor

ynbot commented May 20, 2024

Task linked: AY-5419 Validate Content plugin settings

Copy link
Contributor

@MustafaJafar MustafaJafar left a comment

Choose a reason for hiding this comment

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

It works on my side.
Also, I'm able to modify the settings.
image


I like the idea of this PR.
The way I see it: as long as the plugin exists in core, then its settings should be in core even it's meant to run in side different DCCs.

@iLLiCiTiT iLLiCiTiT merged commit 2faeb0c into develop May 20, 2024
1 check passed
@iLLiCiTiT iLLiCiTiT deleted the enhancement/AY-5419_Validate-Content-plugin-settings branch May 20, 2024 13:18
@@ -770,6 +797,10 @@ class PublishPuginsModel(BaseSettingsModel):
default_factory=ValidateBaseModel,
title="Validate Version"
)
ValidateContainers: ValidateContainersModel = SettingsField(
default_factory=ValidateContainersModel,
title="Validate Containers"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we update the title to Validate Outdated Containers so it matches the label on the plug-in itself?

With just Validate Containers it leaves me a bit guessing what it validates about the containers?

Copy link
Member Author

Choose a reason for hiding this comment

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

Eh, why you wrote it after merge, now I have to create new PR...

Copy link
Collaborator

Choose a reason for hiding this comment

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

Sorry, day off today - saw it a bit too late.

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

Successfully merging this pull request may close these issues.

None yet

5 participants