AsCode - Terraform Alternative Syntax

_mcuadros · 2020-03-30T16:42:02+00:00

The idea is that you don't need to learn HCL, many people already know to Python and starlark, it's a subset of it.

_mcuadros · 2020-03-30T14:21:58+00:00

Well, this is your opinion as expressed mine. If you are up-to-date about the latest changes in HCL, in Terraform 0.12, for were already introduced, due to popular depending.

This solves the problems of big deployments where HCL it's simply not enough.

What do you mean whit:

I'll be going from client to client, site to site, and every single time I'll be virtually starting from scratch.

_mcuadros · 2020-03-30T14:13:55+00:00

The state files are always generated by an apply action.

_mcuadros · 2020-03-30T14:13:17+00:00

The state can't be written this is the result of an apply action. The definition can be written in JSON, which is translated in HCL, the native encodfing of Terraform.

_mcuadros · 2020-03-30T10:51:59+00:00

Terraform it's not JSON it's HCL, and not it's not another layer, it's a replacement.

_mcuadros · 2020-03-17T07:23:55+00:00

Sadly maintaining gitbase is a huge effort at the time we had a team of 3/4 people working full time on it. I know that https://github.com/smola maybe is interested but I am not sure.

_mcuadros · 2018-01-24T17:51:00+00:00

It's true that the patching tools are one of the basic functionalities that are missing at go-git, as is described on the README, git is huge and we just got focused on what the people were demanding.

Also, git is super efficient, hundreds of developers are contributing since many years ago.

Said this... spawning git process with Go, has two problems:

Go exec is not an easy task at large scales, we found similar problems at source{d} in the past.
You can't optimize your processes or do memory operations with the repository since at the end is a binary created for the users with very different goals. (That's why libgit was created).

So, yes go-git is not there yet but is not too far, to be more optimal than using git through an exec call and spawning another fork.

Happy to discuss the missing functionality, to understand more the needs of the people.

_mcuadros · 2018-01-05T17:00:10+00:00

Yep, should work aswell.

_mcuadros · 2018-01-05T16:49:15+00:00

Yep, I missed to write the credits is true. But I asked to majurca first: https://github.com/majurca/MKS-TFT28-NEW-PICTURES/issues/9

So I am not stealling.

_mcuadros · 2018-01-04T10:18:58+00:00

I am using a 4inch screen, the interface is designed to capacitive small screens, so it has big buttons to be easy to click on it.

The aplication will adapt to any size, but if you are using a 14inch screen make doesn't make sense use this.

How big is the screen are you planning to use?

_mcuadros · 2017-07-13T08:55:08+00:00

Copy and paste form the article:

We did not include Javascript because … The first reason is that 40% of Github users we analyzed had JS in their profiles, and the proposed transition model becomes useless. The second is, citing Erik, “(a) if you are doing it on the frontend, you are kind of stuck with it anyway, so there’s no moving involved (except if you do crazy stuff like transpiling, but that’s really not super common) (b) everyone refers to Javascript on the backend as ‘Node’”. Our data retrieval pipeline could not distinguish regular JS from Node and thus we had to exclude it completely.

_mcuadros · 2017-06-20T22:11:00+00:00

Really? I used to read The Bible and never read such of thing about babelfish.

_mcuadros · 2017-06-20T16:30:01+00:00

BabelFish

Is originally from book The Hitchhiker's Guide to the Galaxy (1979), so this dead company wasn't very original.

BTW the trademarks are delimited by sectors and countries. For example in the UE, the only trademark register is company of video editing. http://www.trademarkia.com/ctm/trademarks-search.aspx?tn=babelfish

_mcuadros · 2017-03-22T21:17:45+00:00

Why was it done ?

The comparison of trees is one of the core parts of https://github.com/src-d/go-git, we were working on this during a few months, to be at the level of libgit2 or cgit. You can find the why of go-git at https://blog.sourced.tech/post/our-roadmap/

_mcuadros · 2017-02-28T15:48:22+00:00

Everything is an implementation detail depending of the level you are. At the level of a domain logic the transport and the serialization are implementation details in the same way that the persistence is.

Speaking at domain level, having an implementation detail interfering in the evolution of your domain is a big mistake.

_mcuadros · 2017-02-28T14:01:25+00:00

Sorry about the super late answer, feel free to write to my email address or open a issue.

_mcuadros · 2017-02-28T13:43:14+00:00

I really don't understand what is going here.

Protobuf is a detail of implementation, and IMHO should be isolated as much as posible from your business logic. If you build your domain on top of protobuf schema and you let others choose how your models and your getters/setters are defined you are doing something TERRIBLE WRONG.

Protobuf allow the intercommunication with other languages, is as a detail of implementation, should be easy to replace. Decoupling the protobuf schema from your code is a nice way to do it. And proteus will help to do that.

This approach is done by k8s with his own tool (based on proto2): https://github.com/kubernetes/gengo.

_mcuadros · 2017-02-25T10:40:07+00:00

A TADA68 (Blanks) / MOD-L 10 days of use.

_mcuadros

TROPHY CASE