Open the-it-jaeger opened 1 year ago
once #133 goes in this should test properly /cc @rooftopcellist
@the-it-jaeger can you merge in the current main? It should help with testing
@the-it-jaeger can you please rebase so that the tests pass?
@rooftopcellist I think I rebased properly. I'm not very good at this yet, so please bear with me.
@rooftopcellist I'll write a test case for this upon merging
Ugh. I pushed additional changes related to EEs to the same branch. What's the best way to un-mess that up?
Reverted previous commits. I will make them to another branch and prepare another PR for EE support.
@the-it-jaeger do you want to take a stab at writing the test for it? Example of how they are written are within .github
I can take a stab at it next week. I might call for backup if I get stuck 😅. Dev-y stuff is not my wheelhouse, but I'm willing to learn.
@cooktheryan looking around, it seems I will need to write another AnsibleCredential manifest with .spec.type: Container Registry
, drop it in config/samples/credentials/
and add a kubectl apply -f ...
and a kubectl wait ...
line here:
Am I on the right track?
@the-it-jaeger 100% correct
@cooktheryan : How does this look? ☝️
@rooftopcellist will you please have a look when you can?
@rooftopcellist any chance you have some time to review this?
Bump 😉
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
@cooktheryan @rooftopcellist would either of you be able to review this?
@neevnuv would you take a look at this one? It's been pending for ages.
This should help with #130