Commit Graph

7 Commits

Author SHA1 Message Date
a6e52d9d3d Fix: viper.UnmarshalKey ignores defaults
This seems to be a bug in viper, as soon as we're working with subkeys, things fall apart
2021-08-24 17:03:59 +02:00
ae3b1d0897 First working implementation
- implemented update request processing
- separated host and domain name in config (req. for DNS updates)
- enhanced NFT update validation
- cleaned up example user
- cleand up logging in update request
- moved appropriate config into user request struct
2021-08-24 16:44:52 +02:00
fbf10f9d1b Next implementation steps
- Simplified UpdateRequest to the minimum required
- renamed test user to example
- removed user property from yml config, it is given by the file name.
- splitted server code analogous to command line code so that each handler has its own file.
- made viper confgi in userconfig internal
- added validation to userconfig
- added helper to combaine an IID with a v6net in userconfig
2021-08-23 20:41:32 +02:00
7b93ff425d - Added sample default config (needs manual updating)
- Reworked service and webapi config to Viper unmarshalling
- Added Pretty Printers to config
2021-08-22 14:46:48 +02:00
9a31bbc912 - Clarified web handler name
- Implemented Configuration Loader with unauthorized error handling
- More elaborate test user config
- Use Viper Unmarshalling for User Config loading
- Centralized password hasing code
2021-08-22 14:36:55 +02:00
9f1b9f1690 Refactorization and further implementation
- renamed clientoinfo to updaterequest
- added userconfig skeleton
- added hashed password skeleton
2021-08-21 20:35:08 +02:00
7dd11a0879 First basic version
- NFT and DNS Update skeletons
- Integrated viper configuration management
- Integrated cobra CLI management
- Basic webservice skeleton
2021-08-20 21:10:59 +02:00