Skip to content

Conversation

@tollsimy
Copy link
Contributor

Description

Fix default CrownMails configs.

@tollsimy tollsimy requested a review from a team as a code owner September 30, 2025 18:33
@kingmakerbot
Copy link
Collaborator

Hi @tollsimy. Thanks for your PR.

I am @kingmakerbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

  • /rebase: Rebase this PR onto the master branch
  • /merge: Merge this PR into the master branch
  • /hold: Adds hold label to prevent merging with /merge
  • /unhold: Removes the hold label to allow merging with /merge
  • /deploy-staging: Deploy a staging environment to test this PR (the build-all flag enables user environments building)
  • /undeploy-staging: Manually undeploy the staging environment

Make sure this PR appears in the CrownLabs changelog, adding one of the following labels:

  • kind/breaking: 💥 Breaking Change
  • kind/feature: 🚀 New Feature
  • kind/bug: 🐛 Bug Fix
  • kind/cleanup: 🧹 Code Refactoring
  • kind/docs: 📝 Documentation

@andreabuon andreabuon deleted the crownmails-config branch October 16, 2025 16:08
@frisso
Copy link
Member

frisso commented Nov 5, 2025

/rebase

@andreabuon andreabuon restored the crownmails-config branch November 5, 2025 08:19
@frisso
Copy link
Member

frisso commented Nov 5, 2025

/rebase

1 similar comment
@frisso
Copy link
Member

frisso commented Nov 5, 2025

/rebase

@QcFe
Copy link
Collaborator

QcFe commented Nov 5, 2025

@frisso, bot commands aren't working because the PR wasn't created with the flag to let maintainers make changes to the branch

@frisso
Copy link
Member

frisso commented Nov 5, 2025

@frisso, bot commands aren't working because the PR wasn't created with the flag to let maintainers make changes to the branch

This explains why the "rebase" didn't have any effect, and I didn't know the reason :-(
So @andreabuon would you enable this setting in order to make everything easier? (otherwise you have to make the rebase each time)
Btw, the linking error has already been solved in the master, a rebase would solve that issue immediately.

@andreabuon
Copy link
Contributor

andreabuon commented Nov 5, 2025

@frisso, bot commands aren't working because the PR wasn't created with the flag to let maintainers make changes to the branch

So @andreabuon would you enable this setting in order to make everything easier? (otherwise you have to make the rebase each time)

@frisso It seems like I can't enable that setting because the PR was not opened by me.
We have 2 options:

  • @tollsimy enables that setting
  • I create a new PR from the same branch, making sure that maintainers can make changes to the branch.

In either case, I can take care of rebasing the branch onto master.

@frisso
Copy link
Member

frisso commented Nov 5, 2025

For me, both options are valid.
I would also involve @MarcoRiki , as his new PR looks related to something that is being addressed in this PR as well (I can see some timeout changed in the code). Maybe, we can converge on just one PR that fixes the problems we encountered in the last period.
Thanks!

@tollsimy
Copy link
Contributor Author

tollsimy commented Nov 5, 2025

@frisso @andreabuon
I don't know why but I don't see the flag to allow maintainers to push to the branch. In any case I rebased myself.
After the discussion we had on Slack we agreed to change how CrownMails templates values are set, so this PR would need to be reworked a bit (despite being very easy).

@MarcoRiki
Copy link
Contributor

I can work on this PR and delete the new one

currentInstance := &crownlabsv1alpha2.Instance{}
instanceLookupKey := types.NamespacedName{Name: PersistentInstanceName2, Namespace: tenant.Namespace}
Expect(k8sClient.Get(ctx, instanceLookupKey, currentInstance)).Should(Succeed())
//Expect(k8sClient.Get(ctx, instanceLookupKey, currentInstance)).Should(Succeed())
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
//Expect(k8sClient.Get(ctx, instanceLookupKey, currentInstance)).Should(Succeed())
// Expect(k8sClient.Get(ctx, instanceLookupKey, currentInstance)).Should(Succeed())

CustomDeleteAfterNonPersistent = instautoctrl.NeverTimeoutValue
CustomInactivityTimeoutNonPersistent = "1m"
CustomInactivityTimeoutNonPersistent = "0m"
CustomDeleteAfterPersistent2 = instautoctrl.NeverTimeoutValue
Copy link
Member

Choose a reason for hiding this comment

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

What's the meaning of the number "2" in the name of the variable?

}

tracer.Step("expiration checked")
log.Info("Evaluate remaining time untill expiration", remainingTime, instance.Name)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
log.Info("Evaluate remaining time untill expiration", remainingTime, instance.Name)
log.Info("Evaluate remaining time until expiration", remainingTime, instance.Name)

@frisso
Copy link
Member

frisso commented Nov 5, 2025

I don't have the rights to modify the PR, hence I cannot make my commits directly; please accept my comments, as they are related to linting errors.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants