API: checking name availabiliy for secrets and variables

[nxtcoder19]

Summary by Sourcery

Implement name availability checking for secret variables and enhance the codebase to recognize 'secret_variable' as a resource type.

New Features:

• Add functionality to check name availability for secret variables in the domain logic.

Enhancements:

• Include 'secret_variable' as a recognized resource type in various parts of the codebase, including models and resource mappings.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR implements name availability checking functionality for secrets and variables by adding a new resource type 'secret_variable' and extending the CheckNameAvailability domain method to handle this new type.

Class diagram for ResourceType additions

classDiagram
    class ResourceType {
        <<enumeration>>
        +App
        +ClusterManagedService
        +Config
        +Environment
        +ExternalApp
        +ImagePullSecret
        +ImportedManagedResource
        +ManagedResource
        +Router
        +Secret
        +SecretVariable
        +ServiceBinding
    }
    note for ResourceType "Added SecretVariable to ResourceType enumeration"

Loading

File-Level Changes

Change	Details	Files
Added support for secret variable name availability checking	Added new case in CheckNameAvailability method to handle secret variable resource type Implemented name checking using secretVariableRepo with account name and secret variable name filters	apps/console/internal/domain/names.go
Added new ResourceType for secret variables	Added ResourceTypeSecretVariable constant with value 'secret_variable' Updated IsValid function to include the new resource type in validation	apps/console/internal/entities/resource-mapping.go apps/console/internal/app/graph/model/models_gen.go
Cleaned up deprecated code	Removed commented out legacy code for secretVariableResolver and secretVariableInResolver	apps/console/internal/app/graph/secretvariable.resolvers.go

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @nxtcoder19 - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}