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

Resolve ❌ destinations in connector dependency workflow #20075

Closed
evantahler opened this issue Dec 5, 2022 · 2 comments · Fixed by #20110
Closed

Resolve ❌ destinations in connector dependency workflow #20075

evantahler opened this issue Dec 5, 2022 · 2 comments · Fixed by #20110
Assignees

Comments

@evantahler
Copy link
Contributor

evantahler commented Dec 5, 2022

Just like #19451, we've got a number of destinations that currently have problems in the connector dependency workflow. A good list to work from is here: #19993 (comment).

Screenshot 2022-12-05 at 8 37 48 AM

Of note, the strict-encrypt connectors should not be in the seeds, so we should adjust the python code to know this.

@evantahler evantahler self-assigned this Dec 5, 2022
@erohmensing
Copy link
Contributor

erohmensing commented Dec 5, 2022

I think that may be why they are ⚠️ and not ❌ , but I'd be down to check that extra and for it to be ✅ (not in seed) (expected)

@evantahler
Copy link
Contributor Author

We could make a new status emoji, like 🔵 for "not there, but expected"

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

Successfully merging a pull request may close this issue.

2 participants