-
Notifications
You must be signed in to change notification settings - Fork 7
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: mayadata-io/d-operators
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.28.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: mayadata-io/d-operators
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 49 files changed
- 2 contributors
Commits on Jan 4, 2021
-
feat(crd): use unstructured type inplace of typed crd instance (#187)
This commit makes exhaustive changes to handle CRD instances. CRD instances make use of unstructured types instead of typed instances. Both CRD versions i.e. v1beta1 & v1 are supported. Unstructured instances have proved to be generic & testable versus the typed counterparts especially for CRD schemas that can differ from each other. In other words, CRD schemas have a majority schemaless section that is well handled via unstructured type. This commit also includes a number of integration test cases to avoid bug injections if any. This closes #186 partially. A better approach will be to use latest version of d-operators with clients that make use of unstructured instances directly instead of yaml strings that get converted to go structures. This commit is also a breaking change, since some of the structures have been modified. Clients that are already making use of this structure need to be modified accordingly. Signed-off-by: AmitKumarDas <[email protected]>
Amit Kumar Das authoredJan 4, 2021 Configuration menu - View commit details
-
Copy full SHA for 5fc998d - Browse repository at this point
Copy the full SHA 5fc998dView commit details
Commits on Feb 9, 2021
-
chore(testing): update readme w.r.t programmatic vs declarative testi…
…ng (#188) This commit makes changes to clearly indicate programmatic as well declarative way to test D-operators' Kubernetes controllers. It is important to note that the same model can be followed by other Operators repo if needed. This model has worked fine so far. It makes use of GitHub VM as launching machine & same VM used as a single node K3s cluster to run the tests (both declarative as well as programmatic). Signed-off-by: AmitKumarDas <[email protected]>
Amit Kumar Das authoredFeb 9, 2021 Configuration menu - View commit details
-
Copy full SHA for ad823c7 - Browse repository at this point
Copy the full SHA ad823c7View commit details
Commits on Feb 17, 2021
-
feat(command): add support to delete dependants of command resource (#…
…189) * feat(command): add support to delete dependents of command resource This PR does the following changes: - Add support to delete dependent resources when command resource is deleted. - Add support to launch the jobs periodically when command is configured for run always Signed-off-by: mittachaitu <[email protected]>
sai chaithanya authoredFeb 17, 2021 Configuration menu - View commit details
-
Copy full SHA for a61dfc0 - Browse repository at this point
Copy the full SHA a61dfc0View commit details
There are no files selected for viewing