#general (2021-09)

Thanks for the warm welcome. been following your work for years. great job you guys added alot of value to the whole TF community and were pioneers in the modules path.

yes, unfortunately we haven’t tackled GCP yet

mostly because I’m afraid for us to support 2-3x more modules

there are terraform-google-modules managed by google themselves (vs terraform-aws-modules which is community driven)

https://github.com/terraform-google-modules

Thx,

However, I’m actually looking for some folks to pay them to help me set more custom stuff up

aha, try #jobs

okay

(This can be any field, Dev/Sec/Net/Ops/etc)

Bonus question: if someone had e.g. a CompTIA Security+ certification, but no work experience, would you be sceptical of that? (Security+ is recommended for people with ~2 years of work experience in a related field, though of course you can just train towards the test).

One of my colleagues has the EDT Green Belt. It’s the first one I’ve seen in a while that isn’t just “I know how to study and take a test”. There’s a Black Belt too. Definitely something I want to look into. It starts with a White Belt cert which is a course, and then Green Belt is a self-directed project to apply the principles of White Belt in your own org and present your results.

Having a Green Belt would make me significantly more likely to call, since it shows application of those learned skills in the real world

for someone with 3-6 months it would just be the white belt

Huh! I’ll go have a look, thank you. The White Belt is a certificate of completion, right?

yeah, white is just a class with a cert at the end

Adding to the list

https://www.engineeringthedigitaltransformation.com/white-belt-certification/

The only cert, at that level, I’ve ever sat up and taken notice of is the Red Hat Certified Systems Administrator - because it’s a lab-based exam. You’re locked in a room with a computer that has a bunch of problems - either you know how to fix them or you don’t.

A few friends have taken the OpenShift one from Red Hat. They almost universally said the whole process was a garbage fire. Like, in part of it they expect you to know how to code and build a Ruby application… What??

Huh. I’ve done the RHCSA/RHCE and know others that have - they have a lot of respect for it. But that doesn’t necessarily transpose to their other exams

constraint{ disticnt_property = “${attr.unique.hostname}” value =“{{variable}}”}

Hi Wali, Nomad user here. Hope you found the solution. I think you want to use “spread” instead of constraints?

For nomad queries you might want to try: https://gitter.im/hashicorp-nomad/Lobby https://signup.hangops.com/ (they have a Nomad channel)

looks sweet

Yeah I’m curious to know

1. Whether it is very opinionated about how to do deployments, rollbacks etc, basically does it force you to use a specific process or is it more an integrated set of tools that can use in a umber of ways
2. Whether the open source version will continue to evolve once the company creates their cloud-based subscription plan ;)

We still use it extensively, however, we use it mostly for the build tooling for our ~500+ repos. The codefresh references are out-of-date and not maintained.

Thanks. For some reason, I can’t figure out how to get that target to see the latest tag and increment appropriate. Everything starts with 0.0.0. I’m not sure if I’m misusing it or if there is a setup step I missed.

Can you share the command you are trying to run?

Thanks for the help. I don’t know why I couldn’t figure this out. Here are some things I’ve run:

❯ git checkout 0.1.0
❯ DEBUG=1 make git/export
GIT_COMMIT=970aa6eee682db75508edbc58def6832f21f2ddd
GIT_COMMIT_SHORT=970aa6e
GIT_COMMIT_TIMESTAMP=1631154162
GIT_COMMIT_URL=<REDACTED>
GIT_COMMIT_MESSAGE=<REDACTED>
GIT_COMMIT_AUTHOR=<REDACTED>
GIT_BRANCH=HEAD
GIT_TAG=0.1.0
GIT_BRANCH_TAG=0.1.0
GIT_IS_BRANCH=1
GIT_IS_TAG=1
GIT_TIMESTAMP=1631154162
❯ DEBUG=1 make semver/export
SEMVERSION_COMMIT_SHORT=0.0.0-sha.970aa6e
SEMVERSION_COMMIT=0.0.0-sha.970aa6eee682db75508edbc58def6832f21f2ddd
SEMVERSION_BRANCH=0.0.0-HEAD
SEMVERSION_BRANCH_COMMIT_SHORT=0.0.0-HEAD.sha.970aa6e
SEMVERSION_BRANCH_COMMIT=0.0.0-HEAD.sha.970aa6eee682db75508edbc58def6832f21f2ddd
SEMVERSION_TAG=0.1.0

Maybe I’m not using it correctly. I was expecting to see 0.1.0 show up instead of 0.0.0.

#caption “Good Bot” Thank you

#pr-reviews sounds like its for you

It does! I’m going to join there right away. Thank you.

glad you stopped by to say hi. definitely start to use #pr-reviews for PR submissions. We invite frequent contributors into our contributors group.

So I have been migrating all our Go code into a mono repo and organizing. The angular app though is something different.

• I have a centralized task runner and all the commands needed in root directory.

• For 1-2 of the team they will be focused purely on front end work and only consuming the other build actions. Here’s where I’m confused. For Go, a single module mono repo works perfectly fine. All the linting, formatting, tasks etc all work without changes.

For angular initializing the project directory nests it into it’s own project directory. I think this would mean they’d want to open up the subfolder directly to benefit from the IDE tooling as if it’s a “sub repo”, but I’m not certain.

Any tips on how you’ve laid out a similar back/front end monorepo?

https://classic.yarnpkg.com/lang/en/docs/workspaces/ - to organize code into workspaces

https://lerna.js.org/ - to manage yarn/npm packages for multiple workspaces

https://blog.kintone.io/entry/2020/07/14/103322

and on top of that, https://code.visualstudio.com/docs/editor/workspaces (not related to Yarn workspaces)

I think most are using vscode but can’t guarantee.

These are useful, but a bit much to start with. I have 1 UI project right now and want to figure out the right way to include that in this go monorepo.

Structure

internal
--------- app
--------- ---- app
--------- ---- ---- mypkg
pkg
--- mysharedpkg
cmd
cmd/mybinary1
cmd/mybinary2
build
docker
docs

➡  Now for the angular app, does it get 
angular-proj
--------------- all contents inside here, linter, settings etc?

Or do I put all the contents in root so I know have the angular app directories in root like src/node_modules and such?

I was hoping for the easy first route and then if we start adding more lerna or other refactoring might be good. Just not sure if nesting as a “project” in a subdirectory is best or treat front and backend the same with package.json and such all in root directory of monorepo for now.

I do mostly backend and no one has done mono-repos with front-end here I think, so double checking.

all go to angular-proj

except some top-level package.json deps

that’s why/how lerna will help

I appreciate your help! So basically right a front-end developer would probably open the subfolder and it would “appear” as if it’s own project. That means that they lose out on all the root tasks, editorconfig and other things that would probably load correctly in main directory, but have to be duplicated in a child directory if you were working in directly. I wanted to avoid having issues by pulling up repo vs having to pull up subfolder.

For me to include front-end properly to allow for a new project later, are you saying I should really just plug in Lerna? If so, can I assume I can plug in this angular scaffold easily without breaking stuff?

I was asked by someone about just having a front-end and backend directory, but it felt like more complexity and kinda deviates from normal Go package structures and tooling. Wanted to keep this as flag as I could without causing problems.

What’s the easiest for a team new to this to get used to

nx workspace or lerna ?

I will wrap up the initialization tasks and such, but let me know what you think

lerna and yarn workspaces work together - it’s basically allows you to better manage all the dependencies (in package.json files) without duplication

ok. I have it migrated from npm to yarn already. If I use workspaces, can I assume the dev will pull up the root directory of the repo and be able to work fine from there, no need to do more sub directories in new windows?

And should I be looking at just yarn workspaces (not using those yet), or lerna, or both?

I see lots of folks talking about nx being the better evolution of this, but I’m guessing it’s more complication than I need at this stage

both lerna and yarn (with workspaces). Each dev could work in their own folder, but all the deps would be managed “centrally” fro all sub-projects by lerna+yarn

thank you! I started that path and then found that nx had prebuilt walk throughs for micro-ui frontends with angular so figured I’d switch it up since it’s already documented fully. Appreciate you pointing me towards this!

you welcome. There are many ways of doing it, especially in NodeJs ecosystem

Follow-up. Have everything working except Ng lint. For some reason it doesn’t seem to honor the .eslintrc.json file either in the project level directory or root. Anyone have example of angular.json in root, project directories, and writing eslintrc.json specificied in project root?

Any ideas for typescript pros here?

Another follow-up on this topic…

Wow. Go was easy with a monorepo, but Angular was a major pain (still is). Such a complex beast to get setup right.

Right now we went with yarn workspaces as only 2 projects in the repo, but getting webpack, angular, and yarn workspaces to place nice is painful.

I really like yarn 3 (berry), but I wish Angular played nicer with the PNP and other features, as it’s been a major time suck overall. Probably still worth it, but i’ve questioned my choice plenty of times due to Angular.

yo