teracyhq-incubator/teracy-dev-v05-compat

teracy-dev-v05-compat extension

teracy-dev-v05-compat's Issues

should update manifest to target teracy-dev v0.6.0-a5 and teracy-dev-core v0.4.0

they have been released

should release v0.2.0

it's ready to be shipped

should release v0.1.0

it's ready to be shipped

vagrant gatling-rsync-auto should auto restart when being crashed

From @hoatle on November 22, 2018 9:2

From @hoatle on July 6, 2017 12:15

sometimes it crashed and stopped syncing.

We should auto restart it in this case.

Thinking if we should run it in the background?

Copied from original issue: teracyhq/dev#337

Copied from original issue: teracyhq-incubator/teracy-dev-essential#29

should release v0.5.0

it's ready to be shipped

failed to sync created files from Linux host due to inotify bug

From @hoatle on November 22, 2018 9:1

From @hoatle on June 20, 2017 3:59

egor.k [2:05 AM] 
@hoatle hello again
There is a bug I think, when I create a migration file (I usually duplicate the last one) and then modify it, it doesn't synchronize with virtual machine.
Like this:
1. copy the last migration (with a new folder name of course) - sync works
2. make changes in a new migration's `up.sql` file - sync doesn't work anymore for this file

`vagrant reload` helps, but maybe there is a known way to force all files sync manually or something like this, that doesn't involve rebuild?
I don't create migrations often so it's no very important (edited)

hoatle [7:32 AM] 
thank you @egor.k, sync should work, @phuong please help checking on this

phuong [8:52 AM] 
ok

after triaging, @phuonglm found out that it was a inotify bug and @phuonglm will continue to handle this.

Hopefully this can be fixed by v0.5.0-c1

Copied from original issue: teracyhq/dev#330

Copied from original issue: teracyhq-incubator/teracy-dev-essential#28

should release v0.4.0

it's ready to be shipped

should not register RsyncRecovery when teracy-dev-essential >= 0.3.0 is used

because teracy-dev-essential v0.3.0 handles all of the stuff, we need to check if v0.3.0 is used, do not register the RsyncRecovery in this extension.

should upgrade to use the recent latest version of chef cookbooks

to keep up with the new features, improvements, and bug fixes

should update provisioner name so that we can call each provision with its name

$ vagrant provision --provision-with teracy-dev-v05-compat

should call the chef provision of this extension

should have bash-completion support (at least on Ubuntu)

# temporary solution for https://github.com/teracyhq/dev/issues/388
# install bash-completion if not yet available
if platform?('ubuntu')
  bash 'check exist and install bash-completion' do
    code <<-EOH
      apt-get install bash-completion
      . /etc/bash_completion
      EOH
    not_if { ::File.exist?('/etc/bash_completion') && ::File.exist?('/usr/share/bash-completion/bash_completion') }
  end
end

Support Ubuntu for now, will add more support later.

should add Github Actions CI check for the project

need to add CI check with Github Actions

should release v0.3.0

it's ready to be shipped

should upgrade to use the recent latest version of chef_solo

so that we can avoid any problem with new cookbooks, get more support

Expected: works well with the latest chef version

Given:
Comment the version setting to use the latest chef_solo version

teracy-dev-v05-compat hoatle$ git diff
diff --git a/config.yaml b/config.yaml
index 26a1a47..d7bf787 100644
--- a/config.yaml
+++ b/config.yaml
@@ -65,7 +65,7 @@ nodes:
       - _id: "v05-compat-chef"
         _id_deprecated: 'v05-compat-0'
         name: teracy-dev-v05-compat
-        version: 13.1.31
+        # version  : 13.1.31
         type: chef_solo
         log_level: info
         enabled: true

When $ vagrant up

Then it should work as normal

Actual: it did not work, error reported:

    teracy-dev.local: Installing Chef (latest)...
==> teracy-dev.local: Generating chef JSON and uploading...
==> teracy-dev.local: Running chef-solo...
==> teracy-dev.local: Chef Infra Client cannot execute without accepting the license
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

should port v0.5 features to this extension

so that users can upgrade/migrate easily from teracy-dev v0.5 to teracy-dev v0.6 by:

• each user project should create an extension with yaml config migrating from existsing json config
• using teracy-dev-essential + teracy-dev-v05-compat, user project extensions

and it should be done

should fix chef_solo nodes cache problem

After vagrant up, chef_solo creates a host file under provisioners/chef_solo/nodes with configuration data, however, they're not updated correctly when there is changing configuration.

So the solution is to delete that created file before vagrant up, vagrant reload

should update _id to use key name instead of key index

follow best practices for naming _id

should add files support to copy files

# manage files with file resource: using src as path for content source and dest
# path as the saved destination path
#
# see: https://docs.chef.io/resource_file.html
#
# example:
#
# teracy-dev:
#   # copy certs files for nginx proxy
#   files:
#     - _id: teracy-common-cert-key
#       src: /vagrant/workspace/certs/teracy-local-key.pem
#       dest: /etc/nginx/certs/teracy.local.key
#       owner: vagrant
#       group: vagrant
#       mode: '0755'
#       action: create
#     - _id: teracy-common-cert
#       src: /vagrant/workspace/certs/teracy-local.crt
#       dest: /etc/nginx/certs/teracy.local.crt
#       owner: vagrant
#       group: vagrant
#       mode: '0755'
#       action: create

should support both teracy-dev-essential v0.1.0 and v0.2.0 without any warning message

This is a great example for backward compatibility support

docker-compose was not re-installed when its version config changed

• Given:

  • use teracy-dev v0.6.0-a8
  • create the workspace/teracy-dev-entry/config_default.yaml file with the following content, notice docker-compose.version: '1.25.3':

  teracy-dev:
  
    extensions:
  
      - _id: "entry-v05-compat"
        path:
          extension: teracy-dev-v05-compat
        location:
          git:
            remote:
              origin: https://github.com/teracyhq-incubator/teracy-dev-v05-compat.git
            branch: develop
        require_version: ">= 0.5.0-SNAPSHOT"
        enabled: true
  
      - _id: "entry-essential"
        path:
          extension: teracy-dev-essential
        location:
          git:
            remote:
              origin: https://github.com/teracyhq-incubator/teracy-dev-essential.git
            branch: v0.7.0
        require_version: ">= 0.7.0"
        enabled: true
  
  
      - _id: "kernel-core"
        location: # auto download the extension into the lookup_path
          git:
            remote:
              origin: https://github.com/teracyhq-incubator/teracy-dev-core.git
            branch: v0.4.0
        require_version: ">= 0.4.0"
        enabled: true
  
  
  nodes:
    - _id: "0"
      provisioners:
        - _id: "v05-compat-chef"
          json:
            docker_compose:
              version: '1.25.3' # more: https://github.com/docker/compose/releases/

• When $ vagrant up finished

• Then $ vagrant ssh -c "docker-compose version" should output:

  docker-compose version 1.25.3, build d4d1b42b

• Given updating the docker-compose.version to 1.25.4

• When $ vagrant reload --provision finished

• Then $ vagrant ssh -c "docker-compose version" should output:

  docker-compose version 1.25.4, build xxxxxx

• But actually:

bash: docker-compose: command not found

• Workaround solution: $ vagrant reload --provision one more time

directories should be created with recursive by default

current: error when creating directories with recursive

expected: can create directories with recursive by default

workaround: create a directory by directory

example config:

nodes:
  - _id: "0"
    provisioners:
      - _id: 'v05-compat-chef'
        json:
          teracy-dev:
            directories:
              - _id: "iorad-common-certs-dir"
                path: /etc/nginx/certs
                owner: vagrant
                group: vagrant
                mode: '0755'
                action: create
                recursive: true # TODO: support this

should update to use teracy-dev-essential v0.3.0

• require teracy-dev-essential >= 0.3.0
• remove unused code (related to rsync auto recovery)