enctool VS leapp

https://concise-encoding.org/ is looking for help!

I'm planning to release v1 later this year, and there are still a number of things to finish:

- Finish upgrading the portable testing rig (whereby the tests are defined in CTE format so that they can be run against any implementation).

- Bring the Antlr grammar files up to date and make sure they're as easy as possible to build CTE parsers from.

- Add schema validation support to https://github.com/kstenerud/enctool for Concise Encoding documents (using https://cuelang.org/)

- Critiques on the format itself (passages that are unclear or don't make sense, features that shouldn't be there or need more work, etc)

- Implementations in other languages & platforms (CBE is more important to start because one can always use enctool to convert between CBE and CTE).

It's still in the prerelease stage, but v1 will be released later this year. I'm mostly getting hits from China since they tend to be a lot more worried about security. I expect the rest of the world to catch on to the gaping security holes of JSON and friends in the next few years as the more sophisticated actors start taking advantage of them. For example https://github.com/kstenerud/concise-encoding/blob/master/ce...

There are still a few things to do:

- Update enctool (https://github.com/kstenerud/enctool) to integrate https://cuelang.org so that there's at least a command line schema validator for CE.

- Update the grammar file (https://github.com/kstenerud/concise-encoding/tree/master/an...) because it's a bit out of date.

- Revamp the compliance tests to be themselves written in Concise Encoding (for example https://github.com/kstenerud/go-concise-encoding/blob/master... but I'll be simplifying the format some more). That way, we can run the same tests on all CE implementations instead of everyone coming up with their own. I'll move the test definitions to their own repo when they're done and then you can just submodule it.

I'm thinking that they should look more like:

    c1

Yes, that is exactly the aim of the binary format. It has a few basic concepts like being byte-oriented, 1-byte headers for most things, ULEB128 encoding for large values, same chunking mechanism for all arrays and string-likes, same "open/close" mechanism for all container types, etc.

The binary codec is VERY simple, and can be trivially implemented for an async-safe or otherwise constrained environment. In fact, I expect that many implementations will only build the binary codec, since you could just pass any recorded binary data through enctool [1] or whatever to see or manipulate its contents as a human. An embedded system would have no need to process the text format.

[1]https://github.com/kstenerud/enctool

Summary:

Do you find yourself overwhelmed with work, requests, or complaints and in need of assistance to alleviate the pressure, enhance communication, facilitate organization, prioritize tasks, and foster greater trust and transparency?

Alternatively, I can work as a full stack developer.

AWS Community builder, AWS User group Leader, public speaker (https://www.youtube.com/watch?v=qdu58NAQfU0&t=271s)

Or perhaps you need both? =)

I have 4+ years of experience as a product manager and 8 in product development (before pm: agile coach, UX designer, and developer).

I've been the co-founder of the open-core company behind the OSS project Leapp (https://github.com/Noovolari/leapp)

Please feel free to reach out.

You can switch to saml2aws using the browser method instead of the Okta method and it will continue to work after the upgrade. There is also a really neat GUI tool to manage your session tokens that also works. https://www.leapp.cloud

Take a try to Leapp: https://github.com/Noovolari/leapp

Hello everyone, I'm the maintainer of an open-source DeveloperTool (https://github.com/Noovolari/leapp)

With a heuristic of 7000 users daily, I started feeling the need to have more information on how Users are using the project to improve it.

Is it the right thing to do to create a better Developer Experience and gain feedback for the end users?

On a side:

- For all your employees I can advice you Leapp as open-source project (https://github.com/Noovolari/leapp). It solve mayor of the problem listed here:

I am looking to manage Leapp (https://www.leapp.cloud/) from the StreamDeck. Leapp allows you to manage and switch between different Cloud Accounts (AWS, Azure, etc). Leapp has a command line interface which I could automate with a StreamDeck plugin. Unfortunately it looks like the only official SDK is the sandboxed JavaScript one. This means I cannot automate command line tools with it.

If you’re wondering if there is a tool that allows you to stop thinking about AWS credentials and where to store them in the right way, give a look at Leapp! It takes the responsibility of storing long-term credentials in the system vault, generating/refreshing short-term credentials, and placing them in the right place for the clients to use them.

Still, there is an elementary problem that we need to address, and it’s more on the operational side of things. Once we secured and implemented a tremendous multi-account strategy, how do people access AWS accounts? It turns out there is a fantastic open-source tool that lets you handle that with no effort, and its name is Leapp.

When you have to configure access to multiple AWS accounts using the Assume Role access pattern, it becomes difficult to get rid of all the Named Profiles configuration data and relationships. When you’ve to deal with a complex access scenario, tools like Leapp (https://www.leapp.cloud) come to the rescue! Leapp avoids you to specify relationships between Named Profiles in the config file, as the access methods are stored in the tool-specific configuration file.

Leapp Github repository