crossplane-contrib/function-cue

A crossplane function that runs cue scripts to produce desired resources

function-cue's Issues

Rename crossplane-function-cue to function-cue

Need to:

• rename the existing function-cue repo to function-cue-archived and archive it (@Mitsuwa )
• rename the current repo to function-cue. I think I have access to do this.
• set up the XPKG_ACCESS_ID and XPKG_TOKEN secrets for the repo. Not sure where these come from. (@negz)
• decide on the tag we should use for the first version of the new code. Examples in function-cue have mitsuwa/function-cue:v0.1.2 and latest tag in the elastic repo is v0.1.9. So I propose v0.2.0 as the first tag for this function.
• ensure code coverage works on mainline builds and shows the correct badges

Decide the final form of existing copyright notices in the source code

• Currently we have 16 lines of copyright clauses in every source file
• The opensource team at Elastic has indicated that they would like to see verbiage similar to the following

Copyright 2023-2024 Elasticsearch B.V.
Copyright 2024- The Crossplane Authors.

• Is the above acceptable to everyone? Should we add on to existing text or replace existing text with the above?

cc: @negz @gtback @jamietanna

Create a really simple example for people to get started

The current "simple" example does too many things and is confusing for newcomers.

It has a full-cue codebase + Makefile that could be intimidating for new folks.

We should possibly start with a simple cue script and the rest of the stuff as YAML artifacts such that people who know crossplane but not cue have to only deal with that one new thing.

The second example could demonstrate how everything can be done in cue (which is the current example-simple) and should also be simplified with inputs from crossplane and cue folks.

We should probably also introduce an init subcommand in fn-cue-tools to create a skeleton directory structure with a simple example composition included.